CMP Operational Architecture

Operationally, processes running in CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. need to be submitted, monitored, and assured. Wherever possible, these operational tasks should be automated.

The CMP operational architecture is responsible for submitting, monitoring, and assuring operational processes.

The architecture covers three main areas:

  • Operational Architecture
  • Probes
  • Application Processes

Operational Architecture

In the CMP operational architecture, batch jobs are run and monitored in the Administration ConsoleClosed An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration.. Alert and auditing facilities are also available.

The Administration Console provides the operational teams with an interactive environment, making it simpler for the operations teams to run, manage, and monitor batch server jobs. The Administration Console can be accessed via the operator's web browser:

Probes

The probes feature is a mechanism allowing the execution of predefined queries and the comparison of the query results against pre-configured targets. Probes can be reviewed and managed via the Administration Console.

Audit Logs

The Administration Console Logs facility allows operators to interrogate the persisted log records. These logs are for the entire batch server and also the Administration Console. The filter functionality allows a subset of the logs to be retrieved in order to investigate a specific issue or job.

This document provides a detailed overview of the Administration Console, and lists and describes the CMP batch jobs (process), daemons and probes.

Service Management Responsibilities

CMP requires a service management function to operate. This function is typically responsible for the following key tasks:

  • Process monitoring
    • Responding to alerts from the monitoring system
    • Periodic manual checks for any unmonitored processes
  • Maintaining the batch schedule
    • Managing processes through planned outages, where applicable
  • Data purge and archive in line with agreed schedules
  • Usage error monitoring
  • Payment allocation monitoring
  • System backups

This list reflects the tasks required to manage the CMP application and excludes non-application driven processes such as service level agreementClosed In the Cloud Monetisation Platform, the entity that holds the instructions for generating the bills for one or more subscriptions. including the addresses and how often the bill is generated. (SLAClosed Service Level Agreement. A contract or a part of a contract that defines the services a service provider will provide and the required level or standard for those services.) reporting and monitoring and billing process reviews.